System For Binding An Accessory To A Smartphone Or Tablet PC Application

ABSTRACT

This disclosure relates to software applications particularly for smart phone which are used to control or access hardware, particularly headsets. The software is available at no cost to anyone, but to control its use, it is coded so that only buyers of designated hardware can use it.

TECHNICAL FIELD

This disclosure relates to application software which interfaces with hardware, particularly headsets.

BACKGROUND

As part of a total product offer, a Smartphone or Tablet PC application (app) is offered (free) to customers who purchase a corded and/or wireless headset. Other users should not have access to the Smartphone application. This invention limits the user base of the Smartphone application to those who have purchased the headset of a particular company. The application may run on smartphones or tablet PCs having iOS or Android operating systems.

Furthermore, customers who have purchased a company headset should be limited to only use the application on a limited number of smartphone or tablet devices (say 5). This invention controls that limitation.

The issue is that a smartphone is not able to determine if a corded headset actually is from company or if is from some other vendor, so it cannot uniquely identify the headset.

Furthermore for wireless headsets which can be identified to be from a specific vendor (BT-blue tooth identification), you cannot control how many times a supporting application have been downloaded. This is important if there is a cost associated with each copy of the application.

BRIEF SUMMARY

This summary is to assist the reader in understanding the remaining disclosure and it is not a limitation of the invention.

Disclosed is a system and method for binding an accessory to a smartphone or tablet PC application as shown and described herein.

Also disclosed is a system for binding an headset accessory to a smartphone or tablet pc application comprising the steps of including an ID code with the accessory, linking the accessory to a download data base to download software, requiring the entry of said ID code to commence download, checking to see if the code had previously been used before downloading.

Also disclosed is a method of binding an accessory device to a smartphone or tablet PC application comprising:

-   -   generating a unique code identifying an accessory device type,     -   storing the unique code in a database comprising a number of         generated unique codes     -   extracting a unique code from the database and providing the         code together with the accessory device,     -   downloading the application from an application server to a user         device,     -   entering the unique code on the user device and transmitting it         to the database,     -   verifying the code,     -   if the code is valid, activating the application on the user         device.

Also disclosed is a system for binding an accessory device to a smartphone or tablet PC application comprising:

-   -   a code generator for generating a unique code identifying an         accessory device type,     -   a database storing the generated unique code,     -   an ID card provided with the accessory device and comprising a         generated unique code being configured to activate the         application upon verification of the code.

DESCRIPTION OF THE FIGURES

This disclosure contains FIGS. 1 and 2.

FIG. 1 is schematic drawing of a system according to this disclosure.

FIG. 2 is a table of alternate embodiments.

DETAILED DISCLOSURE

The disclosure comprises:

1. A server (SERVER) that can generate unique codes that have a fixed or variable length so it is practically impossible to “guess” codes. The codes also have encoded which products they belong to. So a company product X can be distinguished from a company product Y directly from the code.

2. A secure database (DATABASE) that stores all the codes, together with a counter that indicates how many times a specific code has been used.

3. A system to extract the codes so that they can be printed (ID CARD) and placed in product in-box packages at the factory.

System:

1. In each box that is shipped, an ID CARD will be included which then connect the headset to the code that is on the ID CARD.

2. When a consumer purchases a headset, and downloads the application from the web (application store) he will be prompted to enter his ID CARD code at first use.

3. When the code is entered the application will contact the DATABASE to verify if the code is in the database list over valid codes.

4. If the code is valid an “OK” will be returned to the user's application and he will then be able to start using the application. The server will register that the application has been downloaded and taken into use one time.

5. If the user downloads the application to a second device, and run the process again, the server will register that the user has taken the application in use on 2 devices. This can be repeated until the maximum number of devices have been reached—after which the server will return “NOT-OK” and further use of the ID CARD code is not possible. The system can recognize a repeat download to the same user (for example before of an installation failure or corruption of the prior download) and allow the user to download again.

6. If in (4) the code is not valid a “NOT-OK” will be returned to the user application, and then the user will not be able to use the application.

7. As the ID CARD code has built-in information on which headset it was shipped with, the application will have that knowledge, and can use that in the application logic and features. The idea could also be stored in the headset in case the card is lost.

ALTERNATIVE EMBODIMENTS

Alternative way would be to build in an ID in the phone to identify which headset it is connecting to (e.g. Bluetooth SMART) though it would add cost. Solving the download limitation issue would have to solved by the user supplying the ID from a headset readout, or connecting the headset to the internet with native software in the headset. 

1. System for binding a headset accessory to a smartphone or tablet pc application: comprising the steps of including an ID code with the accessory, linking the accessory to a download data base to download software, requiring the entry of said ID code to commence download, checking to see if the code had previously been used before downloading.
 2. A method of binding an accessory device to a smartphone or tablet PC application comprising: generating a unique code identifying an accessory device type, storing the unique code in a database comprising a number of generated unique codes, extracting a unique code from the database and providing the code together with the accessory device, downloading the application from an application server to a user device, entering the unique code on the user device and transmitting it to the database, verifying the code, if the code is valid, activating the application on the user device.
 3. A system for binding an accessory device to a smartphone or tablet PC application comprising: a code generator for generating a unique code identifying an accessory device type, a database storing the generated unique code, an ID card provided with the accessory device and comprising a generated unique code being configured to activate the application upon verification of the code. 